(c) Copyright IBM Corporation 1999, 2001. All rights reserved.
(c) Copyright Sun Microsystems, Inc. 1997, 2001. 901 San Antonio Rd., Palo Alto, CA 94303 USA. All rights reserved.
Note: The complete copyright citation is included in the Notices section of this document.
This guide provides information about the IBM OS/2 Warp Developer Kit, Java(TM) 2 Technology Edition, Version 1.3 (Developer Kit). This guide gives information on preparing to install the Developer Kit components, installing the Developer Kit components, and items to note after you install.
The Developer Kit is supported on the following OS/2 products:
Note: For information on FixPak requirements or the IBM FixPak
Web site, see the FixPaks section.
To obtain the IBM build and version number for the Developer Kit, type the following at a command line:
java -version
The Developer Kit consists of two packages: a Runtime Environment and a Toolkit. The Runtime Environment includes such components as JAAS, RMI-IIOP Runtime, and the just-in-time (JIT) compiler. The Toolkit contains such components as a toolkit, the Interactive Code Analysis Tool (ICAT) Debugger, and Samples.
Note: You cannot install the Toolkit unless you are also installing the Runtime.
If you downloaded split files, refer to the Joining Split Files section for information on joining the split files into one installable file.
Before installing the Developer Kit, make a copy of your current CONFIG.SYS file. This ensures that you can return to your original environment if problems occur during installation.
References in this guide are as follows:
The following is a list of the Developer Kit's components and file sizes after installation. You should ensure that sufficient disk space is available before installing.
|
Hardware Requirements:
Software Requirements:
To extract a self-extracting ZIP file, complete the following steps:
If you downloaded split files and need to join them into one installable file, refer to the Joining Split Files section. Information on installing the Developer Kit is located in the Installing the Developer Kit section.
The following considerations apply when installing the Developer Kit:
If you have only one hard disk with a single FAT partition, you have these options:
Note: In this document, the term "partition" refers to any
physical or logical drive.
The following considerations apply:
|
|
|
|
Note: The display and code conversion of the euro are supported on
the code pages containing the euro.
If you want to input the euro, the single-byte character set (SBCS) version of OS/2 is required. The U.S. International keyboard, UX103, supports input of the euro, but a standard English keyboard does not. In all cases, if you do not have a keyboard that supports input of the euro, you are able to display it, but you are not able to input it.
For information about downloading a particular FixPak, visit the IBM
FixPak Web site at:
http://ps.software.ibm.com/pbin-usa-ps/getobj.pl?/pdocs-usa/otherservices.html
Installing the Developer Kit as the default Java Virtual Machine (JVM) allows you to execute the Developer Kit from a command prompt by default. You can either make the Developer Kit your default JVM permanently or temporarily. See the following sections for more information.
To modify the PATH statement, add x:\JAVA13\JRE\BIN; to the PATH statement
in your CONFIG.SYS file.
If you decide to keep a previous version of Java as the default JVM, do not check the checkbox during the
GUI install or, if the Developer Kit is already installed, do not add the x:\JAVA13\JRE\BIN;
directory to the PATH statement in your CONFIG.SYS file. If you already have a 1.1.x version of Java
installed as the default JVM, it will remain as the default JVM.
Note:
You may improve performance by removing references to previous releases of Java in the CONFIG.SYS file.
However, there are known applications that will fail if you install the Developer Kit (version 1.3) as your default JVM.
See the Known Limitations Section section for more information.
If the Developer Kit is not installed as the default JVM, but you want to use it in a Java session, modify the PATH statement. For example,
SET PATH=x:\JAVA13\JRE\BIN;%PATH%
x is the drive where you installed the Developer Kit.
You may improve performance by modifying the BEGINLIBPATH and CLASSPATH statements as follows:
SET BEGINLIBPATH=x:\JAVA13\JRE\BIN;x:\JAVA13\JRE\DLL;%beginlibpath%
SET CLASSPATH=
Notice that the CLASSPATH is set to a null value because the Developer Kit's JVM does not generally require the CLASSPATH to find system
class files; CLASSPATH is used for application class files.
If the Developer Kit is installed as the default JVM, but you want use a Java 1.1.x JVM in a Java session, modify the PATH statement. For example,
SET PATH=x:\JAVA11\BIN;%PATH%
x is the drive where you installed the Developer Kit.
If you removed the JAVA11 references from the CONFIG.SYS file, you need to modify the PATH, BEGINLIBPATH, and CLASSPATH statements as follows:
SET PATH=x:\JAVA11\BIN;%PATH%
SET BEGINLIBPATH=x:\JAVA11\BIN;x:\JAVA11\DLL;%beginlibpath%
SET CLASSPATH=x:\JAVA11\LIB\CLASSES.ZIP;x:\JAVA11\SWING\SWINGALL.JAR;\;
Notice that the CLASSPATH is set to the Java 1.1.x library files. The CLASSPATH setting for individual systems will differ.
To make the Developer Kit and the Java Plug-in execute, you must modify the PATH as shown above.
If you have installed the Developer Kit (version 1.3) as your default Java Virtual Machine (JVM) and you have:
You must:
The following list contains information about using the Developer Kit and Netscape Communicator v. 4.04 and higher:
You cannot install the Developer Kit if you are running Netscape Communicator while executing the INSTALL command. You must close Netscape Communicator and then execute the INSTALL command.
To run applets using Netscape Communicator v. 4.04, you must have the just-in-time (JIT) compiler turned on. However, if you want to have the JIT turned off and still use Netscape Communicator v. 4.04, you will need the latest refresh level of Netscape Communicator v. 4.04. For information on the latest refresh level, visit the following Web site:
If you have Netscape Communicator v. 4.61 and have not downloaded the
latest refresh, you may experience "ghost" checkboxes during installation.
Although these "ghost" checkboxes do not affect the installation of the
Developer Kit, you might want to download the latest refresh from the following
Web site:
http://ps.software.ibm.com
You can join the split files using the Merge Utility or manually from a command prompt. The following subsections provide information on how to join the split files into one installable file.
Before you begin, be sure:
Before you begin the process of joining the split files, you must download the Joiner Utility to the same directory as the split files that you downloaded. (The file name is joiner.exe.) The Joiner Utility contains the Merge Utility, which allows you to join the split files into one installable file. The Joiner Utility can be downloaded from the same page as the Developer Kit components on the Software Choice Catalog of Features.
Type joiner at a command prompt from within the directory
where you downloaded the Joiner Utility. This command extracts the Merge Utility
(merge.exe) and its required data files. You will use the Merge Utility to join
the split files.
Type the following at a command prompt from within the directory where you downloaded the Joiner Utility:
merge
This recreates any packages that are split into multiple files. To install the file, see the Installing the Developer Kit sections
copy /b javainrt.ex1 + javainrt.ex2 + javainrt.ex3 javainrt.exe
This recreates any packages that are split into multiple files. To install the file, see the Installing the Developer Kit sections
The following sections give instructions and information about installing the Developer Kit. Before you install the Developer Kit or components associated with it, read the Before You Install section for information on extracting the files and the installation requirements.
Note: If you have Netscape Communicator running
while installing the Developer Kit, the installation will fail. You must shut down Netscape Communicator and then
begin the installation process.
You can install the Developer Kit using either the desktop method or the command prompt method. See the following sections for instructions.
Note: If you have Netscape Communicator running
while installing the Developer Kit, the installation will fail. You must shut down Netscape Communicator and then
begin the installation process.
To install using the INSTALL.EXE object, follow these steps:
The INSTALL.EXE command brings up a Graphical User Interface (GUI) with buttons specifying the languages that you can install the program in. Click the language you prefer, and the installation program leads you through the installation steps.
A Developer Kit for OS/2 folder is created in the Programs folder on OS/2 Warp 4 and on the Desktop in OS/2 Warp Server and OS/2 Warp 3.
After the installation is complete, if you want to clean up the directory in which the Developer Kit files were extracted, select the DELINST.CMD object from the Developer Kit folder. This removes the Developer Kit files and subdirectories from the directory where they were extracted. Files and subdirectories not extracted from the Developer Kit are not erased. You may also manually delete the files you downloaded.
Note: If you have Netscape Communicator running
while installing the Developer Kit, the installation will fail. You must shut down Netscape Communicator and then
begin the installation process.
To start installation, make sure that you are in the directory where the Developer Kit files were extracted. At the OS/2 command prompt, type:
INSTALL
The install command brings up a GUI with buttons specifying the languages that you can install the program in. Click the language you prefer, and the installation program leads you through the installation steps.
A Developer Kit for OS/2 folder is created in the Programs folder on OS/2 Warp 4 and on the Desktop in OS/2 Warp Server for e-business.
After the installation is complete, if you want to clean up the directory in which the Developer Kit files were extracted, select the DELINST.CMD object from the Developer Kit folder. This removes the Developer Kit files and subdirectories from the directory where they were extracted. Files and subdirectories not extracted from the Developer Kit are not erased. You may also manually delete the files you downloaded.
If you are using the GUI to install the Developer Kit and components are not selectable, you might not have downloaded and extracted the ZIP file containing the component you need. Return to the Software Choice Catalog of Features page and download the self-extracting ZIP file that you need.
All components of the Developer Kit require that you download and install the Runtime Environment component (or have previously installed the Runtime Environment component) and restarted the system.
If your installation of the Developer Kit fails, check for and delete any remaining installation objects. If you do not delete these installation objects, future installations could fail with a message stating that one or more components could not be installed because the object is read-only or in use by another process.
For a Configuration, Installation, and Distribution (CID) install, the icon for the installation object is a blue box with a red ribbon and is located on the desktop. For an attended installation, the object is in the x:\os2\install\ folder (where x is the boot drive). To delete the object, click the object using the right mouse button, and click Delete on the menu.
Alternately, go to the directory containing the object, and delete the entire directory tree. The directory is named either "Install object" or "Java 1.3 for OS!2" depending on when the installation failed.
After deleting the installation object, shut down and restart the system.
If, after following the instructions listed above, the install object was not removed, do the following:
If you are certain that your system meets the required FixPak levels, but are unable to install due to the automated FixPak checking, you may disable the automated FixPak checking. To do this, use either of the following methods:
Method One:
Method Two:
disablecheck="NO"Change the "NO" to "YES". (This statement is located on or about line 12.)
Note: Feature Install version
1.2.3 or later is required for Unattended (CID) installations. Also, if you have Netscape Communicator running
while installing the Developer Kit, the installation will fail. You must shut down Netscape Communicator and then
begin the installation process.
Unattended or Configuration, Installation, and Distribution (CID) installations of the Developer Kit are handled by a command-line interface to Feature Install (CLIFI), and can take 15 to 20 minutes or more. After the installation program finishes, the system must be restarted to complete the installation.
CLIFI requires two response files: the Developer Kit response file (JAVA130.RSP) and a customized response file where users can override the default selections. The CID.RSP file is included in the installation package as an example of the customized response file; this file and CID.CMD file need to be modified for unattended installations.
Where appropriate, the CID.RSP file contains variables that allow you to select which components to install and the target drive and directory. By default, the CID.RSP file is set to install all the components of Developer Kit. You can modify this response file to select which components you want to install. Be sure to download and extract all of the files you need before you start the installation. Also, if you install the Toolkit, install the Runtime Environment as well, even if the Runtime Environment is already installed.
The following table lists the selectable components and variable names:
|
In the CID.RSP file, set "selection=1" for each component you want to install, and set "selection=0" for each component you do not want to install. For example, to:
Java13.Continue=UNATTENDED
Java13.LicenseAgree=DISAGREE
JV13Runtime.Selection=1
JV13RuntimeConfig.Selection=1
JV13RuntimeUrls.Selection=1
JV13NSFiles.Selection=1
JV13MZFiles.Selection=1
Java13.RUNDRV=x:
JV13DefaultJVM.Selection=1
JV13Samples.Selection=0
JV13SamplesConfig.Selection=0
JV13Samplesurls.Selection=0
JV13Samples.SMPDRV=x:
JV13Toolkit.Selection=0
JV13ToolkitConfig.Selection=0
JV13Debugger.Selection=1
JV13Debuggerurls.Selection=1
JV13Debugger.DBGDRV=x:
This is an example. See the CID.RSP file for specific components
and their associated variables. x is the drive where the component
is installed.
There is a JV13xxConfig.Selection variable associated with each JV13xx.Selection variable. The JV13xxConfig.Selection variable must be set to the same value as the JV13xx.Selection variable. For example, if you set JV13Toolkit.Selection=0, you must also set JV13ToolkitConfig.Selection=0 (where xx is the component name).
In the example above, there are several variables that must be set to have the Developer Kit install properly. The variables and their definitions are:
|
To suppress the confirmation windows during installation, set the following variable as shown:
java13.continue=UNATTENDED
The Toolkit is installed to the \JAVA13 directory on the target drive. If you install the Toolkit, the Runtime Environment is automatically installed to the same drive as the Toolkit. The Runtime Environment is a prerequisite for the Toolkit, Samples, and Debugger components.
The target drive for the Samples and ICAT components is specified by setting the drive to the desired values. If the Developer Kit exists on the target drive, the installation program replaces it.
The CID.CMD file contains a sample CLIFI command for a CID installation. The installation process has been modified to include a multilingual installation; therefore, you must specify your language variable in the CID.RSP files. The language variables are as follows:
|
The CLIFI command can also be entered as a single-line command at an OS/2 command prompt, as shown below:
clifi /a:c /r2:cid.rsp /r:xx\JAVA130.rsp /b:c: /s:d:\tmp\xx
/l1:ciderr.log /l2:cidhist.log
Use the following variable list as a reference in setting the variables in the files mentioned above.
Where:
|
To suppress the confirmation windows during installation, set the following variable as shown:
java13.continue=UNATTENDED
If you received a "successful" CID return code after the installation of the Developer Kit, but the installation failed, it might be because:
It is recommended that CID administrators complete a FixPak check to ensure that the correct FixPak level is available. (See the FixPaks section for more information.) You can use the check.cmd file located in the x:\Java13 directory as an example for writing a script that checks for FixPak levels. (x:\ is the drive where the Developer Kit is installed.)
If you are certain that your system meets the required FixPak levels, but are unable to install due to the automated FixPak checking, you may disable the automated FixPak checking. To do this, use either of the following methods:
Method One:
Method Two:
disablecheck="NO"Change the "NO" to "YES". (This statement is located on or about line 12.)
Note: If you have Netscape Communicator running
while installing the Developer Kit, the installation will fail. You must shut down Netscape Communicator and then
begin the installation process.
A NetView(R) Distribution Manager/2 (NVDM/2) CID installation requires creating a profile and then building and cataloging a change file. The NVDM/2 profile allows you to specify only one response file; however, the Developer Kit unattended installation requires two response files. In addition, variable and argument handling in NVDM/2 is different from that used in Feature Install, which is used to install the Developer Kit.
In the following section are two methods that you can use to install the Developer Kit using NVDM/2.
In the NVDM/2 profile, specify all the CLIFI options in the PARMS variable. The parameters must be on a single line and enclosed in double quotation marks:
Program=c:\os2\install\clifi.exe
Parms="/a:c /r2:cid.rsp /r:\xx\JAVA130.rsp /b:c: /s:d:\tmp\xx
/l1:ciderr.log /l2:cidhist.log"
This method requires you to modify the profile whenever the source directory or log file names are changed. Alternatively, you could replace these values with workstation-specific variable values, as shown below:
Program=c:\os2\install\clifi.exe
Parms="/a:c /r2:$(ResponseFile) /r:$(SourceDir)\xx\JAVA130.rsp
/b:c: /s:$(SourceDir\xx) /l1:$(LogFile1) /l2:$(LogFile2)"
ResponseFile=$(WorkstatName).rsp
SourceDir=d:\tmp
LogFile1=$(WorkstatName).log
LogFile2=$(WorkstatName).lg2
This second method requires a separate response file for each workstation and requires WorkstatName to be set appropriately.
Use the following variable list as a reference in setting the variables in the files mentioned above.
Where:
|
Note: If you have Netscape Communicator running
while installing the Developer Kit, the installation will fail.
You must shut down Netscape Communicator and then
begin the installation process.
The WorkSpace On-Demand 2.0 product includes Java 1.1.6 for OS/2 Warp. You can install the Developer Kit (version 1.3) on WorkSpace On-Demand servers and clients. The Developer Kit coexists with Java 1.1.x for OS/2 Warp. See the following sections for installing the Developer Kit on WorkSpace On-Demand servers and clients and information on installing the Developer Kit as the default JVM.
To install the Developer Kit on a WorkSpace On-Demand server, use the GUI. See the GUI Installation Method section of this guide for instructions.
To install the Developer Kit on a WorkSpace On-Demand Client, use an unattended (CID) installation. You can use the instructions in the Unattended (CID) Installation Method section and use the CID.CMD and WSOD2.RSP files that are included in the Developer Kit installation package. The steps for installation are completed on a WorkSpace On-Demand 2.0 server.
Note:
If you want to install the Developer Kit as your default JVM on WorkSpace
On-Demand clients, references to the z:\JAVA13 directories and files need
to be placed before the z:\JAVA11 references in the CONFIG.SYS file.
Complete the following steps:
To complete the unattended install, see the following sections.
To enable the Developer Kit's Runtime Environment component, a WorkSpace On-Demand administrator must make the following additions to the CONFIG.SYS files for the WorkSpace On-Demand clients:
Add:
|
You can find and edit the CONFIG.SYS file for WorkSpace On-Demand Clients based on the following two options:
[rpldrive]:\ibmlan\rpl\machines\[client name]\config.sys
[rpldrive]:\ibmlan\rpl\machines\BB20.xx\[machine class]\config.sys
Where:
|
To enable the Runtime Environment, a WorkSpace On-Demand administrator must make the following addition to the File Index Table (FIT) files for the WorkSpaces On-Demand clients:
Add:
z:\JAVA13 BB20.xx\JAVA13You can find and edit the FIT files for WorkSpace On-Demand Clients based on the following two options:
[rpldrive]:\ibmlan\rpl\fits\[client_name].FIT
[rpldrive]:\ibmlan\rpl\fits\DFBB20xx.FIT
A WorkSpace On-Demand administrator also must grant read and execute access to the JAVA13 directory for the WorkSpace On-Demand clients:
Run the following LAN Server commands:
NET ACCESS [rpldrive]\ibmlan\rpl\bb20.xx\JAVA13 /ADD RPLGROUP:RX NET ACCESS [rpldrive]\ibmlan\rpl\bb20.xx\JAVA13 /APPLY
Where:
|
The USER_HOME directory for the Developer Kit needs to have read/write access as this is where security certificates and plug-in properties files are created and accessed. For example, to specify z:\JAVA13_RW as the USER_HOME directory and to give it read/write access, add the following to the FIT file (this must be entered as one continuous line):
z:\JAVA13_RW \\server_name\WRKFILES\client_name\JAVA_RW
Substitute the names of the WorkSpace On-Demand server and client for server_name and client_name. z is the drive where you installed the Runtime Environment. This could also be entered in the default FIT file.
A WorkSpace On-Demand administrator must also make the following addition to the OS2.INI files for the WorkSpace On-Demand clients. The addition should be NULL terminated.
Add: Application = Java13
Key = USER_HOME
Value = z:\JAVA13_RW
See the WorkSpace On-Demand 2.0 Handbook for information on how to use an INI Editor or the NET APPPARM Command to add INI file entries for WorkSpace On-Demand Clients. You can find the OS2.INI file for WorkSpace On-Demand Clients one of two ways:
[rpldrive]:\ibmlan\rpluser\[client name]\os2\os2.ini
[rpldrive]:\ibmlan\rpl\machines\BB20.xx\[machine class]\os2\os2.ini
Where:
|
To enable fonts for the Runtime Environment, a WorkSpace On-Demand administrator must make the following additions to the OS2.INI files for the WorkSpace On-Demand clients. All additions should be NULL terminated. z specifies the drive where the Runtime Environment is installed for the client.
Add:
Application = PM_Fonts Key = courtbi_.ttf Value = z:\JAVA13\jre\lib\fonts\COURTBI_.TTF Application = PM_Fonts Key = courtb__.ttf Value = z:\JAVA13\jre\lib\fonts\COURTB__.TTF Application = PM_Fonts Key = courti__.ttf Value = z:\JAVA13\jre\lib\fonts\COURTI__.TTF Application = PM_Fonts Key = court___.ttf Value = z:\JAVA13\jre\lib\fonts\COURT___.TTF Application = PM_Fonts Key = devamt.ttf Value = z:\JAVA13\jre\lib\fonts\DEVAMT.TTF Application = PM_Fonts Key = devamtb.ttf Value = z:\JAVA13\jre\lib\fonts\DEVAMTB.TTF Application = PM_Fonts Key = lucb.ttf Value = z:\JAVA13\jre\lib\fonts\LUCB.TTF Application = PM_Fonts Key = lucbb.ttf Value = z:\JAVA13\jre\lib\fonts\LUCBB.TTF Application = PM_Fonts Key = lucbbi.ttf Value = z:\JAVA13\jre\lib\fonts\LUCBBI.TTF Application = PM_Fonts Key = lucbi.ttf Value = z:\JAVA13\jre\lib\fonts\LUCBI.TTF Application = PM_Fonts Key = lucs.ttf Value = z:\JAVA13\jre\lib\fonts\LUCS.TTF Application = PM_Fonts Key = lucsb.ttf Value = z:\JAVA13\jre\lib\fonts\LUCSB.TTF Application = PM_Fonts Key = lucsbi.ttf Value = z:\JAVA13\jre\lib\fonts\LUCSBI.TTF Application = PM_Fonts Key = lucsi.ttf Value = z:\JAVA13\jre\lib\fonts\LUCSI.TTF Application = PM_Fonts Key = luct.ttf Value = z:\JAVA13\jre\lib\fonts\LUCT.TTF Application = PM_Fonts Key = luctb.ttf Value = z:\JAVA13\jre\lib\fonts\LUCTB.TTF Application = PM_Fonts Key = luctbi.ttf Value = z:\JAVA13\jre\lib\fonts\LUCTBI.TTF Application = PM_Fonts Key = lucti.ttf Value = z:\JAVA13\jre\lib\fonts\LUCTI.TTF Application = PM_Fonts Key = thonbi__.ttf Value = z:\JAVA13\jre\lib\fonts\THONBI__.TTF Application = PM_Fonts Key = thonburi.ttf Value = z:\JAVA13\jre\lib\fonts\THONBURI.TTF Application = PM_Fonts Key = thonb___.ttf Value = z:\JAVA13\jre\lib\fonts\THONB___.TTF Application = PM_Fonts Key = thoni___.ttf Value = z:\JAVA13\jre\lib\fonts\Thoni___.TTF
See the WorkSpace On-Demand Handbook 2.0 for information on how to use an INI Editor or the NET APPPARM Command to add INI file entries for WorkSpace On-Demand Clients. You can find the OS2.INI file for WorkSpace On-Demand Clients based on the following two options:
[rpldrive]:\ibmlan\rpluser\[client name]\os2\os2.ini
[rpldrive]:\ibmlan\rpl\machines\BB20.xx\[machine class]\os2\os2.iniWhere:
|
To install the Java Plug-in for the Netscape 4.x browser, a WorkSpace On-Demand administrator must copy the npjava.dll file to the WorkSpace On-Demand clients' Netscape 4.x Plug-in directory.
copy d:\JavaTemp\package\npjava.dll [rpldrive]:\ibmlan\rpl\bb20.xx\NETSCAPE\PROGRAM\PLUGINS\*.*To install the Java Plug-in for the IBM web-browser for OS/2, copy the npoji6.dll file to the WorkSpace On-Demand clients' Web-browser Plug-in directory.
copy d:\JavaTemp\package\npoji6.dll [rpldrive]:\ibmlan\rpl\bb20.xx\os2\os2web\PLUGINS\*.*Where:
|
In addition, a WorkSpace On-Demand administrator must make the following addition to the OS2.INI files for the WorkSpace On-Demand clients. All additions should be NULL terminated.
Add:
Application = Java Plug-in
Key = JAVA_HOME
Value = z:\JAVA13\jre
Where z specifies the drive where the Runtime Environment is installed for the client.
See the WorkSpace On-Demand Handbook 2.0 for information on how to use an INI Editor or the NET APPPARM Command to add INI file entries for WorkSpace On-Demand Clients. You can find the OS2.INI file for WorkSpace On-Demand Clients one of two ways:
[rpldrive]:\ibmlan\rpluser\[client name]\os2\os2.ini
[rpldrive]:\ibmlan\rpl\machines\BB20.xx\[machine class]\os2\os2.iniWhere:
|
If you want to install components other than the Runtime Environment for the WorkSpace On-Demand client, you can select these components in the WSOD2.RSP file.
If you install the Toolkit, a WorkSpace On-Demand administrator
must make the following additions to the CONFIG.SYS files for the clients.
Add:
|
where z:\JAVA13 is the drive and directory where the Toolkit is installed for the client.
The WorkSpace On-Demand server administrator must add the following lines to the RPL\FITS\client_name.FIT file to give the WorkSpace On-Demand client the ability to run the samples provided in the Samples component:
z:\JAVA13\WEBLOGS \\server_name\WRKFILES\client_name\JAVA13\WEBLOGS z:\JAVA13\HOTJAVA \\server_name\WRKFILES\client_name\JAVA13\HOTJAVA
Substitute the names of the remote IPL server and the remote IPL client for server_name and client_name. z is the drive where you installed the Developer Kit. This could also be entered in the default FIT file.
The remote IPL clients can compile the sample code if the samples are placed in a directory to which the remote IPL client has write access.
If you are issuing a trust (giving access) to connect to a Web server, the IDENTITYDB.OBJ file needs to be read/write. Add the following to the FIT file to make the connection:
z:\JAVA13\WEBLOGS \\server_name\WRKFILES\client_name\JAVA13\WEBLOGS z:\JAVA13\HOTJAVA \\server_name\WRKFILES\client_name\JAVA13\HOTJAVA z:\JAVA13\IDENTITYDB.OBJ \\server_name\WRKFILES\client_name\JAVA13\IDENTITYDB.OBJ
On a WorkSpace on Demand client system, the following command is added to the CONFIG.SYS file if version 1.1.6 of the Developer Kit was installed during the WorkSpace On-Demand Server installation:
set java_compiler=xxxThis command turns off the just-in-time (JIT) compiler.
To turn the JIT compiler on, remove the command listed above from your CONFIG.SYS file. You can find and edit the file based on the following two options:
[rpldrive]:\ibmlan\rpl\machines\[machine class]\config.sys
[rpldrive]:\ibmlan\rpl\machines\BB20.xx\[machine name]\config.sys
Use the following variable list as a reference in setting the variables in the files mentioned above:
Where:
|
To create a public application for the Java Plug-in Control Panel that runs on WorkSpace On-Demand 2.0 client, you need to provide access to the Netscape files. The access controls are specified in the Netscape APPPOST.FIT file.
The following example shows how to create a public application for running the Java Plug-in Control Panel:
net app jctrlpnl /remark:"Java Plug-in Control Panel"
/appdir:z:\java13\jre\bin
/command:"jctrlpnl.cmd"
/type:wsod /interface:pm /add
net appparm jctrlpnl NCC_POSTFITS=z:\netscape\program\apppost.fit
/add /placement:b
z:\java13 is where the Java Developer Kit image is installed and z:\netscape is where the Netscape image is installed.
Before you begin the installation process, check for or do the following.
To install the Developer Kit on the client machines, you need to complete the steps in the following Creating an Application Package and Distributing the Developer Kit Application Package to the Client Machines sections.
To complete the installation process and distribute the Developer Kit to your WorkSpace On-Demand 3.0 clients, you need to create an application package for the Developer Kit on your sandbox client. To do this, complete the following steps:
net use x: \\[AppServ\os2apps]Where [AppServ\os2apps] is the name of the application server and the netname for the OS/2 applications.
z:\applcptr\crtpkg /startWhere z is the WorkSpace On-Demand 3.0 client boot drive.
NETSCAPE -k file:///index.htm
net use x: \\[AppServ\os2apps]Where [AppServ\os2apps] is the name of the application server and the netname for the OS/2 applications. Verify that the Developer Kit is functioning correctly by typing:
x:\JAVA13\jre\bin\java -version
z:\applcptr\crtpkg [JavaApp1] /finishWhere [JavaApp1] is the name of the Developer Kit application package.
For information on DBCS installation considerations, see the Installing the Developer Kit on a DBCS OS/2 WorkSpace On-Demand 3.0 Sandbox Client section.
Now that you have created a Developer Kit application package on the sandbox client, you are ready to distribute that application package to the other client machines. To do this, complete the following steps:
The \\AppServ\os2apps\JAVA13\JRE directory (the USER_HOME directory) needs to have read/write access because this is where security certificates and plug-in properties files are created and accessed.
To create the read/write access, create a FIT file to map to this directory and create APPPOST.FIT in the application's executable directory (where the application's .exe file resides).
For example, if java.exe is the application's .exe file, then create the APPPOST.FIT file in \\AppServ\os2apps\JAVA13\JRE\BIN. To give read/write access to this directory, add the following lines to the file:
;APPFIT ; required for application FITS
?:\JAVA13\JRE \\<DCSERVER>\TDMPRFLS\<USER>\OS2\<LANG>\PROFILES\JAVA13\JRE
The second line needs to be entered as one continuous line.
cd \TDM\TDMPKGS\APPLICATION\OS2\EN
md JavaApp2
copy JavaApp1\APPPARM.INI JavaApp2\*.*
A remote IPL installation requires creating two response files and setting up the appropriate directories and files on the remote IPL server.
Follow these steps for each client to be installed:
After placing the extracted Developer Kit installation files on the remote IPL server, the GENFIRPL command is used to generate two response files: FILES.RSP for the remote IPL server and JAVA130.RSP for the remote IPL client. The following is a sample GENFIRPL command. The command should be entered on a single line.
genfirpl /m:c:\javacode\xx /r:c:\ibmlan\rpl
/u:c:\ibmlan\rpluser /f:c:\javacode\xx\JAVA130.rsp
/c:client_name /b:x:
The remote IPL client must not be running when the GENFIRPL command is issued. One GENFIRPL command must be done for each remote IPL client, specifying the appropriate client name and boot drive.
Use the following variable list as a reference in setting the variables in the file(s) mentioned above:
Where:
|
The JAVA130.RSP file contains variables that allow you to select which components to install and the drive and directory. By default, the JAVA130.RSP file is set to install all the components of Developer Kit. You can modify this response file to select which components you want to install. Be sure to download and extract all of the files you need before you start the installation.
You need to use a text editor that handles lines greater than 255 bytes, such as TEDIT, to prevent truncation of the long lines in this file. Because this file is very large, modifications can be time consuming and error-prone. Make a backup copy of JAVA130.RSP before modifying it to prevent loss of data.
The client_name.FIT file for each remote IPL client must be modified to include the following, which must be entered on a single line:
z:\os2\install\install.inv \\server_name\WRKFILES\client_name
\os2\install\install.inv
Substitute the name of the remote IPL server and remote IPL client for server_name and client_name. z is the drive where you installed the Developer Kit.
Remote initial program load (RIPL) installations are handled by CLIFI (the Feature Install installation program) and can take 15 to 20 minutes or more. After logging on to the remote IPL server as an administrator, run the CLIFI command using the response file created for the remote IPL server FILES.RSP:
clifi /a:i /r:c:\javacode\files.rsp
It is necessary to restart the remote IPL Server after running CLIFI if file transfer has not been suppressed.
Run the CLIFI command on each remote IPL client after you run the GENFIRPL command for that client.
clifi /a:i /r:z:\xx\JAVA130.rsp
Use the following variable list as a reference in setting the variables in the files mentioned above.
Where:
|
The remote IPL server administrator must add the following lines to the RPL\FITS\client_name.FIT file to give the remote IPL client the ability to run the samples provided in the Samples component:
z:\JAVA13\WEBLOGS \\server_name\WRKFILES\client_name\JAVA13\WEBLOGS
z:\JAVA13\HOTJAVA \\server_name\WRKFILES\client_name\JAVA13\HOTJAVA
Substitute the names of the remote IPL server and the remote IPL client for server_name and client_name. z is the drive where you installed the Developer Kit.
The remote IPL clients can compile the sample code if the samples are placed in a directory to which the remote IPL client has write access.
If you are issuing a trust to connect to a Web server, the IDENTITYDB.OBJ file needs to be read/write. Add the following to the FIT file to make the connection:
z:\JAVA13\WEBLOGS \\server_name\WRKFILES\client_name\JAVA13\WEBLOGS
z:\JAVA13\HOTJAVA \\server_name\WRKFILES\client_name\JAVA13\HOTJAVA
z:\JAVA13\IDENTITYDB.OBJ \\server\WRKF\client\JAVA13\IDENTITYDB.OBJ
Substitute the names of the remote IPL server and the remote IPL client for server_name and client_name. z is the drive where you installed the Developer Kit.
This can also be entered in the default FIT file as part of the installation of the Developer Kit for WorkSpace On-Demand when running the WSOD.CMD command.
The following sections provide additional information that you might need after you install the Developer Kit.
The objects in the following list are displayed in the Developer Kit OS/2 folder only if you are running OS/2 Warp Server 4. If you are running OS/2 Warp Server for e-business, you can access the associated documents at the locations shown.
If you installed the Toolkit or ICAT Debugger for OS/2 Java components in different directories from the Runtime Environment component, specify the appropriate directory for these two objects. The links to the Runtime Environment documentation and the ICAT Debugger for OS/2 Java do not work if the components are in different directories or are not installed.
After the initial installation of the Developer Kit, you can install additional components by re-running the installation procedure. This requires that you either download the files from the Software Choice Web site again, keep all of the extracted files on your system, or keep the original ZIP files and extract the files again when needed.
The AWT TextField and TextArea controls do not support characters outside of the current code page. Users running on U.S. English systems can switch to code page 850 (the multilingual code page, which supports the Western European languages) to see additional language characters in these controls.
Modifying the font properties files provided with the Developer Kit is not supported.
If you have problems with time in your Java applets, you might need to set or change the timezone (TZ) variable. To set the TZ variable, do one of the following:
In a standard OS/2 environment, the maximum virtual address space available to an application is 512 MB, and the memory available for the Java heap size is limited to approximately 256 MB. This restriction can be modified by using OS/2 High Memory Support (OS/2 HMS). OS/2 HMS increases the maximum virtual address space available to an application to three GB.
The following platforms support OS/2 HMS:
The available High Memory is controlled by the VIRTUALADDRESSLIMIT setting in the CONFIG.SYS file. The value is specified in MBs in the CONFIG.SYS file. For example:
VIRTUALADDRESSLIMIT=2048
The smallest value allowed is 512 MB. This provides compatibility with previous versions of OS/2 that allowed access to 512 MB. Values in excess of 512 MB can reduce the number of processes that can concurrently run on a system.
To indicate to the Java Virtual Machine (JVM) that it should attempt to place its heap into OS/2 HMS, set the following environment variable:
SET JAVA_HIGH_MEMORY=1
If OS/2 HMS is not available, this option is ignored and the heap is allocated from the standard address space.
If the Java heap is placed in OS/2 HMS, the objects allocated from it are not accessible to 16-bit code. This is only a problem if a Java application has native method DLLs that are either compiled with a 16-bit compiler or call other DLLs that contain 16-bit code.
OS/2 TCP/IP, prior to version 4.1, has this limitation. OS/2 TCP/IP 4.1 or later must be installed if OS/2 HMS heaps are used.
This release includes the BigDecimal class (com.ibm.math.BigDecimal). It is provided (with its supporting class MathContext) as an alternative to the java.math.BigDecimal class. If you are using the java.math.BigDecimal class in a Java program and you want to access the new class, you must change the import statement in your source code as shown below.
Change:
import java.math.*;
To:
import com.ibm.math*;
You do not need to change any other code.
The following sections give information on installing and using the Java Plug-ins for Netscape 4.x and IBM Web browser for OS/2.
If you installed Netscape Communicator after the Developer Kit and want to enable the Java Plug-in, complete the following steps:
Use the following variable list as a reference in setting the variables in the files mentioned above.
Where:
|
If you installed the IBM Web-browser for OS/2 after the Developer Kit and want to enable the Java Plug-in for this browser, complete the following steps:
|
After the Java Plug-in is installed, you can control the behavior of the Java Plugin at runtime. For example, when you run the Java Plug-in, you can control whether to bring up the Java Console on startup of the Java Plug-in.
The Control Panel is a Java application launched by the command file located in the [x:\JAVA13]\jre\bin\jctrlpnl.cmd. An icon for this command file is located in the [x:\JAVA13] directory. Where x is the drive where you installed the Developer Kit. By default, JAVA13 is the directory name.
A Just-in-Time (JIT) compiler is provided with the Developer Kit. The JIT compiler generates machine code for frequently used byte code sequences in a Java application or applet during execution. The JIT is enabled by default. You can disable the JIT to aid in the isolation of a problem with a Java application, an applet, or the compiler itself by passing the following command to the Java runtime interpreter:
SET JAVA_COMPILER=none
This command works in both 1.3 and 1.1.x Developer Kit environments.
There are some short file names based on the 8.3 file name convention required by OS/2 that differ from the long file names required by such platforms as Windows(R) or Linux. Below are the known file names that differ:
|
To set up the applet viewer to connect through a proxy gateway to the Internet:
Http proxy server: myproxy.mycompany.com
Http proxy port: 80
If your Web browser is already configured to connect to the
Internet, use the values set up in that configuration. For example,
with WebExplorer, use the Proxy Gateway values in the Configure
Servers page, omitting the leading 'http://' and trailing '/'.
You can specify Java options and system properties by creating an environment variable called IBM_JAVA_OPTIONS and setting it to the values you require. Any Java options or system properties specified must be preceded by a space, except for the first option. For example, you could set IBM_JAVA_OPTIONS as follows:
IBM_JAVA_OPTIONS=-Dmysysprop1=tcpip -Dmysysprop2=wait
If you specify the same options or properties from the command line (or from a JNI program), then these will take precedence over the options and properties specified by the IBM_JAVA_OPTIONS environment variable. The only exception to this rule is when specifying -Xt, -Xtm, or -Xdebug, all of which imply that no JIT should be used.
Be aware that:
The system property ibm.jvm.bootclasspath allows an additional search path to be defined. The value of this property is inserted between any value defined by -Xbootclasspath/p: and the bootclass path. The bootclass path is either the default, or that defined using the -Xbootclasspath: option. For further information regarding these options, see 3.1 Additional Sources of Information
Java Remote Method Invocation (RMI) provides a simple mechanism to do distributed Java programming. RMI over IIOP (RMI-IIOP) extends the base Java RMI to perform communication using the Common Object Request Broker Architecture (CORBA) standard Internet Inter-ORB Protocol (IIOP protocol). This allows direct interaction with any other CORBA Object Request Brokers (ORBs), whether they were implemented in Java or another programming language.
The Developer Kit includes support for applications developed to use RMI over IIOP (RMI-IIOP). This support is part of the standard Runtime Environment installation and requires no special setup or configuration.
An IDL-to-Java compiler is included with this release. This tool translates CORBA Interface Definition Language (IDL) to Java. See the IDL-to-Java Compiler User's Guide for further information. This documentation can be found in:
[x:\JAVA13]\RMI-IIOP\DOCS\toJavaPortableUG.htm
[x:\JAVA13] is the drive and directory where you installed the Developer Kit. By default, JAVA13 is the name of the directory.
The IDL-to-Java compiler supports the CORBA 2.3 specification. This includes the "valuetype" construct and its mapping from IDL to Java. Details of this support can be found at the following FTP sites:
The IDL-to-Java compiler is provided so that you can experiment with the IDL generated by the "rmic -idl" command. This generated IDL and the IDL-to-Java compiler are not required when using RMI-IIOP in the Java to Java case. The generated IDL is used to allow RMI-IIOP to interoperate with other languages such as C++. For interoperation with C++, an IDL-to-C++ compiler that supports the CORBA 2.3 specification must be used to compile the generated IDL.
The following considerations apply when using the IDL-to-Java compiler:
The following are known IDL-to-Java compiler problems:
interface t {
const long foo = 1;
attribute long foo;
};
interface A { struct S { short s; }; };
interface B:A { typedef S new_S;
exception ex {S f1;}; // Error for "S" here
};
For information on IBM and RMI-IIOP, see the following IBM Web site:
http://www.ibm.com/java/jdk/rmi-iiop/index.html
Other documentation available:
[x:\JAVA13] is the drive and directory where you installed the Developer Kit. By default, JAVA13 is the name of the directory.
|
The Java 2 platform provides a means to enforce access controls based on where code came from and who signed it. These access controls are needed because of the distributed nature of the Java platform where, for example, a remote applet can be downloaded over a public network and then run locally.
However, the Java 2 platform does not provide a way to enforce similar access controls based on who runs the code. To provide this type of access control, the Java 2 security architecture requires and following:
For a general overview of JAAS, see the following Web site:
From this main page, click Products & APIs and scroll down to the Optional Packages section. The documents at this Web site contain links to many other Web-based information sources.
The IBM version of JAAS for OS/2 differs from the Sun version of JAAS for Windows in that the com.sun.* packages have been moved to com.ibm.* packages.
The following gives information on the location of the JAAS files:
JAVA13\jre\bin:
jaas.dll
jaas_g.dll
Note: The Runtime Environment is installed in the x:\JAVA13 directory. (Where x is the drive where you installed the Developer Kit. By default, JAVA13 is the name of the directory.)
Java objects can be accessed from a C program using the Java Native Interface (JNI), which was new with Java 1.1.1. Using the JNI provides a more stable interface than the previous Native Method Interface (NMI).
JNI applications usually need to interact with the long, float, and double Java types for one or more of the following reasons:
For each of the Java types, the JNI provides native types that you can use in your JNI application. These types are shown in the following table.
Note: that there is no need to use these types if your application does
not manipulate the Java types long, double, and float.
|
||||||||||||||||
Use the JNI native types when defining a native method implementation so that the compiler will match the native method signature with that in the header file generated by using the javah utility.
The JNI native types jlong, jdouble, and jfloat are incompatible with the respective C/C++ types long, double, and float. If you attempt to cast one to the other, you will get either a compile error or unexpected behavior at runtime. Do not attempt to convert one to the other as the formats of the JNI native types are private to the Developer Kit.
The JNI header file (jni.h) includes another header file that is shipped with the Developer Kit named int64_md.h. This file defines helper functions and macros that you can use to work with the native types.
The functions and macros in int64_md.h (relating to jlong) typically include ll either at the start or the end of the name. The functions relating to jdouble or jfloat typically include dbl, double, flt, or float in the name. There are also some jlong, jdouble, and jfloat constants defined.
The following are macro examples:
If you downloaded one or more of the font packages as one file, skip to the Installing Additional Fonts sections for installation instructions. If you downloaded split files, follow these steps to join the split files into one, installable file. Then, continue to the installation sections.
Copy /b ExamFont.txx + ExamFont.txx + ExamFont.txx ExamFont.ttfWhere:
|
See the following sections for installation information using the CID installation method or the OS/2 Font Palette method.
Note: If CLIFI requests you to "insert the media", then
you need to either set the /s: parameter correctly in the wtfnt.cmd file
or place the PACKAGE.CTL file in the same directory as the font packages
that you want to install.
Use the following variable list as a reference in setting the variables in the files mentioned above.
Where:
|
To install an additional font using the Font Palette, follow these steps:
The following sections describe known double-byte character set (DBCS) considerations.
When installing the Developer Kit on DBCS versions of OS/2, DBCS characters might not be displayed on the installation panels or the lines could exceed the right border of the display window, even when the window is maximized.
To correct these problems, exit the installation program, open the Netscape Navigator or Netscape Communicator for OS/2 object, and select the Options menu item. Open the General Preferences notebook and select the Fonts tab. Choose the proper encoding for your country and then set the proportional and fixed fonts to MINCHO. Click OK to save the changes. When you start the installation of the Developer Kit again, the text should be displayed correctly.
On Simplified or Traditional Chinese systems, ensure that all available OS/2 TrueType fonts are installed. To install these fonts, do the following:
C:\OS2\INSTALL\INSTALLA panel titled "System Configuration" is displayed.
The appropriate fonts should be installed. Restart your system when the font installation is completed.
Some DBCS users may encounter the following behaviors relating to Asian Input Method operation. To download the Program Temporary Fixes (PTFs) or FixPak listed below, contact your local IBM Service Representative.
The following table describes behaviors relating to Asian Input Method operation and the DBCS system affected.
|
Based on the descriptions listed above, the following table shows the PTF level needed if you are using OS/2 Warp 4.
|
Based on the descriptions listed above, the following table shows the FixPak level needed if you are using OS/2 Warp Server for e-business.
|
Users in some countries could unexpectedly see Arabic number characters appear. Some country-specific versions of OS/2 map the characters x'00B0' through x'00B9' to the Arabic numbers zero (0) through nine (9). To see the desired characters, change the Bi-directional Attributes in CONFIG.SYS or use the Language page in the Properties notebook (Settings notebook in OS/2 Warp Server for e-business) of the object to obtain the desired effect.
Use the following Japanese environment settings for OS/2 Warp 4 Japanese version:
|
To run the Developer Kit, the following fonts are required on your system:
|
You can check them in the Font Palette, which is in the System Setup folder in the OS/2 System folder.
These fonts can be installed through the Selective Install program object, which is in the Install/Remove folder in the System Setup folder on OS/2 Warp 4 systems and OS/2 Warp Servers for e-business.
On OS/2 Warp Server for e-business, you can improve the font quality of a small point size font by enabling an association between an outline font and a bitmap font. To enable the association, do the following:
If you would like more information on bitmap font association, click the help button located on the Associate to Bitmap Font page.
If you have an Windows NT system application server, the following error may occur if you are running the WorkSpace On-Demand 3.0 CRTPKG utility while creating an application package for the Developer Kit on a DBCS OS/2 WorkSpace On-Demand 3.0 Sandbox Client:
CRT0071: Can't search directory "z:\OS2\install" - DosFindFirst/DosFindNext returned error 161.
CRT0005: Fail to create system snapshot.
This error is a result of the name of the last directory or file in the z:\OS2\install directory containing a '5C' byte. The installation of the Developer Kit creates a directory in z:\OS2\install. This name, when translated into English, means "Installed Features". Delete or rename this directory and then run the CRTPKG utility. You should be able to correctly create an application package for the Developer Kit.
The following sections give you information on uninstalling the Developer Kit.
If you have installed components of the Developer Kit multiple times without uninstalling those components, references to JAVA13 continue to exist in your CONFIG.SYS file. If you want those references to be removed, delete them from your CONFIG.SYS file.
Note: If you have Netscape Communicator running
while uninstalling the Developer Kit, the uninstall will fail.
You must shut down Netscape Communicator and then begin the uninstall process.
To uninstall using the Remove the Developer Kit object, follow these steps:
If you extracted any additional fonts files or Java Plug-in files like the plugin.exe or mzplugin.exe, and you want to remove them from your system, go to the drive and directory where you installed them and delete them.
To start uninstalling, make sure that you are at the root drive where the Runtime Environment is installed. At an OS/2 command prompt, enter:
JAVA13/UNINSTAL/UNINSTAL
The uninstall program leads you through the uninstallation process. Only files and directories created by the installation process are removed. For instance, the HOTJAVA directory created by running the Applet Viewer is not removed during uninstallation.
If you extracted any additional fonts files or Java Plug-in files like the plugin.exe or mzplugin.exe, and you want to remove them from your system, go to the drive and directory where you installed them and delete them.
Support for uninstalling the Developer Kit requires access to an inventory object (Java 1.3) in the Installed Features directory (\os2\install\installed features). If you install the Developer Kit for both the WorkSpace On-Demand 2.0 client and the WorkSpace On-Demand 2.0 server, the Java 1.3 inventory object is damaged or replaced. Therefore, do not use the uninstall program to remove the Developer Kit components from the client space.
Instead, delete the [rpldrive]\ibmlan\rpl\bb20.xx\JAVA13 directory structure and any references made to this directory that were added to the WorkSpace On-Demand client image directories. (Such as the CONFIG.SYS, OS2.INI, and FIT files.)
To remove the Developer Kit from the server, delete the \JAVA13 directory structure. You can delete the directory structure from the Drives folder in the OS/2 System folder.
To uninstall the Developer Kit, enter the following single-line command at an OS/2 command prompt:
clifi /a:u /f:"<WP_INSTALLED>" /o:INV_JAVA13 /set:Selection=ALL
To remove or replace the Developer Kit as your default JVM, remove the x:\JAVA13\JRE\BIN; statement from your PATH statement in your CONFIG.SYS file. For the change to take effect, restart the system.
copy x:\JAVA13\jre\bin\*.exe to x:\JAVA13\binWhere x is the drive where you installed the Developer Kit. By default, JAVA13 is the name of the directory.
If you apply a service level to the Developer Kit, repeat the above step after the service level is applied.
(c) Copyright International Business Machines Corporation 1999, 2001. All rights reserved.
(c) Copyright Sun Microsystems, Inc. 1997, 2001. 901 San Antonio Rd., Palo Alto, CA 94303 USA. All rights reserved.
U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1758
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the information. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this information at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
JTCMAIL@uk.ibm.com
[Hursley Java Technology Center (JTC) contact]
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurement may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
All IBM prices shown are IBM's suggested retail prices, are current and are subject to change without notice. Dealer prices may vary.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written.
These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces.
This edition applies to version 1.3 of the IBM OS/2 Warp Developer Kit, Java(TM) Technology Edition and to all subsequent releases and modifications until otherwise indicated in new editions.
This software is based in part on the work of the Free Type Project. For more information about the Free Type Project, see: http://www.freetype.org
The following terms are trademarks of International Business Machines Corporation in the U.S., or other countries, or both:
IBM
OS/2
OS/2 Warp
NetView
Java is a trademark of Sun Microsystems, Inc. in the U.S. and other countries. The Java technology is owned and exclusively licensed by Sun Microsystems, Inc.
Netscape and Netscape Navigator are trademarks of Netscape Communications Corporation.
Intel and Pentium are registered trademarks of Intel Corporation in the United States and other countries.
Tivoli is a registered trademark of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks of others.